Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e7f5d29e35c8d6c2018f4c592c564939db0fa38e77f2165301ffc6a3be3a93

Tx prefix hash: aafb5a3f883aff32152a6d571d3567d2d7a10688f900018b04cc81f04cb684d2
Tx public key: d0d3ba2f91ed83bf4e2c2f8fb99f1c57931de5f45529d8ad22dcb5f2e91e6def
Timestamp: 1722444553 Timestamp [UCT]: 2024-07-31 16:49:13 Age [y:d:h:m:s]: 01:156:03:47:56
Block: 1077819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370182 RingCT/type: yes/0
Extra: 01d0d3ba2f91ed83bf4e2c2f8fb99f1c57931de5f45529d8ad22dcb5f2e91e6def02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e8f7e7572811c43ec9f22015a83fb5eaedeb76de81aff794339690466ffac0 0.600000000000 1550374 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": 1077829, "vin": [ { "gen": { "height": 1077819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e8f7e7572811c43ec9f22015a83fb5eaedeb76de81aff794339690466ffac0" } } ], "extra": [ 1, 208, 211, 186, 47, 145, 237, 131, 191, 78, 44, 47, 143, 185, 159, 28, 87, 147, 29, 229, 244, 85, 41, 216, 173, 34, 220, 181, 242, 233, 30, 109, 239, 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