Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 463bb5bdabb48590357e77321f38820007e023b2ccd2665e1b3152aa9efbd9a4

Tx prefix hash: 7b06f0e6ba1e1b278efb8c08d292dae735e7005ea9dbd63ab501e6c3de69bbbe
Tx public key: 08ef8c630edf62ce1263916abc4c4ebe226d0d44caf5e73086af964a29301624
Timestamp: 1695530670 Timestamp [UCT]: 2023-09-24 04:44:30 Age [y:d:h:m:s]: 01:206:14:38:24
Block: 854890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408726 RingCT/type: yes/0
Extra: 0108ef8c630edf62ce1263916abc4c4ebe226d0d44caf5e73086af964a2930162402110000000533af99f4000000000000000000

1 output(s) for total of 0.902390673000 dcy

stealth address amount amount idx
00: a466e67e01165aa5e4869f002233d75c651c25ce2e9dde2761b037753fb84419 0.902390673000 1308884 of 0

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": 854900, "vin": [ { "gen": { "height": 854890 } } ], "vout": [ { "amount": 902390673, "target": { "key": "a466e67e01165aa5e4869f002233d75c651c25ce2e9dde2761b037753fb84419" } } ], "extra": [ 1, 8, 239, 140, 99, 14, 223, 98, 206, 18, 99, 145, 106, 188, 76, 78, 190, 34, 109, 13, 68, 202, 245, 231, 48, 134, 175, 150, 74, 41, 48, 22, 36, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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