Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 581a55d1b8837d30104a8419f5ca8d8f3a847a4e97d7eeb01aa6363c082ec07e

Tx prefix hash: cfcb8ec6c60fc3501f397eeff99479078e7fbc1b6b6286df91960b39814fe94b
Tx public key: edf5467d17ef3aa068b5196959a1ecf69bc342d2ec5a6106acff7c2ca1d4aef7
Timestamp: 1714979491 Timestamp [UCT]: 2024-05-06 07:11:31 Age [y:d:h:m:s]: 00:330:03:15:11
Block: 1015940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235970 RingCT/type: yes/0
Extra: 01edf5467d17ef3aa068b5196959a1ecf69bc342d2ec5a6106acff7c2ca1d4aef702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aa981819fa230614025d0c5d5f06eeba6707d8565a5058b0fc370385e4800a7 0.600000000000 1479383 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": 1015950, "vin": [ { "gen": { "height": 1015940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aa981819fa230614025d0c5d5f06eeba6707d8565a5058b0fc370385e4800a7" } } ], "extra": [ 1, 237, 245, 70, 125, 23, 239, 58, 160, 104, 181, 25, 105, 89, 161, 236, 246, 155, 195, 66, 210, 236, 90, 97, 6, 172, 255, 124, 44, 161, 212, 174, 247, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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