Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989fce11308a6b866e19da3528df232e20ceedabef9a279b0acd88aeb348ac47

Tx prefix hash: 830944d43dd714331c45bdb53dbeb1d3cbac98ec3d71ff2d2094f9b4e68669b0
Tx public key: 8b8e2bd89c902c71b8297df893b76549b1162afb9ad43854fb238eadd2d9b908
Timestamp: 1737065462 Timestamp [UCT]: 2025-01-16 22:11:02 Age [y:d:h:m:s]: 00:151:21:49:25
Block: 1198890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108280 RingCT/type: yes/0
Extra: 018b8e2bd89c902c71b8297df893b76549b1162afb9ad43854fb238eadd2d9b90802110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f9b87ec0e793092394347e9d15bb7a5f4cc14d559ed845f22bca5753b2cd16c 0.600000000000 1685517 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": 1198900, "vin": [ { "gen": { "height": 1198890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f9b87ec0e793092394347e9d15bb7a5f4cc14d559ed845f22bca5753b2cd16c" } } ], "extra": [ 1, 139, 142, 43, 216, 156, 144, 44, 113, 184, 41, 125, 248, 147, 183, 101, 73, 177, 22, 42, 251, 154, 212, 56, 84, 251, 35, 142, 173, 210, 217, 185, 8, 2, 17, 0, 0, 0, 15, 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