Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5f1d03b3d0848dacc120e14e25295c26d52ad493b41985845c3554363d8d8a

Tx prefix hash: 634d552527d97afb16d3dd0c6b093541a8cf85482fcf10b0f1fa17861010f07e
Tx public key: e9650df154a1d8d032df2741221e28bb3b0598f33fb3a837ff41b8478152fca8
Timestamp: 1720942181 Timestamp [UCT]: 2024-07-14 07:29:41 Age [y:d:h:m:s]: 01:123:02:04:43
Block: 1065377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346484 RingCT/type: yes/0
Extra: 01e9650df154a1d8d032df2741221e28bb3b0598f33fb3a837ff41b8478152fca802110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96f2628cfc460b0537811fc08ccab27965ba9435cbc1fe7704658f44f3dc7936 0.600000000000 1535922 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": 1065387, "vin": [ { "gen": { "height": 1065377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96f2628cfc460b0537811fc08ccab27965ba9435cbc1fe7704658f44f3dc7936" } } ], "extra": [ 1, 233, 101, 13, 241, 84, 161, 216, 208, 50, 223, 39, 65, 34, 30, 40, 187, 59, 5, 152, 243, 63, 179, 168, 55, 255, 65, 184, 71, 129, 82, 252, 168, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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