Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e41632e32234ecd4233e3858892546e74deb188485cf269bde6238ae0fbacda4

Tx prefix hash: 67709125fe7dc3155e13ea2e188561891c73dfc0590cf48cc3fd838dda175220
Tx public key: d5e5ac41df2c840a365a610c2f1b6a847d4a61bbc810c6a246e273dab12954bd
Timestamp: 1709458145 Timestamp [UCT]: 2024-03-03 09:29:05 Age [y:d:h:m:s]: 01:106:18:17:06
Block: 970162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337227 RingCT/type: yes/0
Extra: 01d5e5ac41df2c840a365a610c2f1b6a847d4a61bbc810c6a246e273dab12954bd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bda65441bdc3968f3174118e3ba03c710b4a351e5445877b8c81c57728b2bde0 0.600000000000 1430011 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": 970172, "vin": [ { "gen": { "height": 970162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bda65441bdc3968f3174118e3ba03c710b4a351e5445877b8c81c57728b2bde0" } } ], "extra": [ 1, 213, 229, 172, 65, 223, 44, 132, 10, 54, 90, 97, 12, 47, 27, 106, 132, 125, 74, 97, 187, 200, 16, 198, 162, 70, 226, 115, 218, 177, 41, 84, 189, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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