Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3d7ed1d16203d232e7e33c93ad8317d4de08f912ac14c809829ad27bd49eefd

Tx prefix hash: f7438f772a1829c8d7513bd2086d475d0209a5f2ced530c60ca2e1db6f8b8a4b
Tx public key: a4360c551b3dde22573c1b79b90ee6411d9c734012641bdc729f87e1ad4200f2
Timestamp: 1723905520 Timestamp [UCT]: 2024-08-17 14:38:40 Age [y:d:h:m:s]: 00:291:21:41:53
Block: 1089938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208551 RingCT/type: yes/0
Extra: 01a4360c551b3dde22573c1b79b90ee6411d9c734012641bdc729f87e1ad4200f202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e4e3e237709f2bb41f21da082bdac7119239de47335d74c9e7d909598d1b0b0 0.600000000000 1564561 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": 1089948, "vin": [ { "gen": { "height": 1089938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e4e3e237709f2bb41f21da082bdac7119239de47335d74c9e7d909598d1b0b0" } } ], "extra": [ 1, 164, 54, 12, 85, 27, 61, 222, 34, 87, 60, 27, 121, 185, 14, 230, 65, 29, 156, 115, 64, 18, 100, 27, 220, 114, 159, 135, 225, 173, 66, 0, 242, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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