Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5209fc46d0b49e6f2b23b37068b1bae5943f98cdd2c32340e76eab08935d584

Tx prefix hash: cebc7cb1151e05990f0bd4b3dc3a46ea4e7336ed72090f68e17c609130d5d4d3
Tx public key: e9c228afec86a5ca3963998940b4cb161fb100d94b886c1e36f79dd4f5bc367c
Timestamp: 1728132347 Timestamp [UCT]: 2024-10-05 12:45:47 Age [y:d:h:m:s]: 00:177:04:22:19
Block: 1124975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126420 RingCT/type: yes/0
Extra: 01e9c228afec86a5ca3963998940b4cb161fb100d94b886c1e36f79dd4f5bc367c02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ce7681de1812a29cd36a97184c35ca3e4f6996f0092c7fa770fdd98c5ce52c6 0.600000000000 1607648 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": 1124985, "vin": [ { "gen": { "height": 1124975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ce7681de1812a29cd36a97184c35ca3e4f6996f0092c7fa770fdd98c5ce52c6" } } ], "extra": [ 1, 233, 194, 40, 175, 236, 134, 165, 202, 57, 99, 153, 137, 64, 180, 203, 22, 31, 177, 0, 217, 75, 136, 108, 30, 54, 247, 157, 212, 245, 188, 54, 124, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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