Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f09f59f9afeb5a2bd4502ea27a9ed9fa7f2f451b8f464e7200e60ef896b460

Tx prefix hash: bd0024b7c527bef66fbcc382cb59ce446354705d5bb4f27564dcbe9349748a91
Tx public key: 15a8d0c41172d0ba54802a83176211149ab861f3d6944cd608a6fbdf5ffe81ae
Timestamp: 1705400214 Timestamp [UCT]: 2024-01-16 10:16:54 Age [y:d:h:m:s]: 01:080:12:53:57
Block: 936497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318659 RingCT/type: yes/0
Extra: 0115a8d0c41172d0ba54802a83176211149ab861f3d6944cd608a6fbdf5ffe81ae02110000000479bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86eec7f2c5e44ac7543dcc0bb0e044d48328db8124dae4e7dc7e4e74a08fd607 0.600000000000 1394525 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": 936507, "vin": [ { "gen": { "height": 936497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86eec7f2c5e44ac7543dcc0bb0e044d48328db8124dae4e7dc7e4e74a08fd607" } } ], "extra": [ 1, 21, 168, 208, 196, 17, 114, 208, 186, 84, 128, 42, 131, 23, 98, 17, 20, 154, 184, 97, 243, 214, 148, 76, 214, 8, 166, 251, 223, 95, 254, 129, 174, 2, 17, 0, 0, 0, 4, 121, 189, 163, 190, 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