Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 506172b83f75e1b6939ea3c0626b120d0faa476ea30a41e6b1bf353583d790c1

Tx prefix hash: 4aad6ad9dba1d034ae36e235685470946b2724366a6fb75ba85d65809ca0b0f9
Tx public key: a782e3071dac8265d3f9fb9d9d97bb1bcc63e6ac8cb9d13540506ac6810ec73b
Timestamp: 1703764355 Timestamp [UCT]: 2023-12-28 11:52:35 Age [y:d:h:m:s]: 01:317:05:23:33
Block: 922956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485553 RingCT/type: yes/0
Extra: 01a782e3071dac8265d3f9fb9d9d97bb1bcc63e6ac8cb9d13540506ac6810ec73b0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 263616f7228ed266b8ff831403a68b22031d12e3f0548481b4f7df7fa026d864 0.600000000000 1380662 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": 922966, "vin": [ { "gen": { "height": 922956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "263616f7228ed266b8ff831403a68b22031d12e3f0548481b4f7df7fa026d864" } } ], "extra": [ 1, 167, 130, 227, 7, 29, 172, 130, 101, 211, 249, 251, 157, 157, 151, 187, 27, 204, 99, 230, 172, 140, 185, 209, 53, 64, 80, 106, 198, 129, 14, 199, 59, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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