Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fa17b688447de736a426cad1c05f312f460d06d9e29c6648927cbe51898e6cc1

Tx prefix hash: e1f4332373b7a4b48585d7bff9f1ee820b7af7666b0931ec92bd5a76695030cc
Tx public key: f58b9d2df7eea641323ddea85217d0b77b1c267797888c24bfd3bc1be237f12b
Timestamp: 1735637491 Timestamp [UCT]: 2024-12-31 09:31:31 Age [y:d:h:m:s]: 00:314:22:39:20
Block: 1187070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222595 RingCT/type: yes/0
Extra: 01f58b9d2df7eea641323ddea85217d0b77b1c267797888c24bfd3bc1be237f12b021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0957485e38bd44d87efd27af9b942c7a66477e816a0e2541f879f3f7b6760a61 0.600000000000 1673557 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1187080, "vin": [ { "gen": { "height": 1187070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0957485e38bd44d87efd27af9b942c7a66477e816a0e2541f879f3f7b6760a61" } } ], "extra": [ 1, 245, 139, 157, 45, 247, 238, 166, 65, 50, 61, 222, 168, 82, 23, 208, 183, 123, 28, 38, 119, 151, 136, 140, 36, 191, 211, 188, 27, 226, 55, 241, 43, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8