Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f0b72ca3f240488e09cb78e52f3896b708a8c0812775bb570808b304326d88

Tx prefix hash: 69526c8fd8eb829a17946dc2d81b0b39d7c128767a2071bf32b6d76fe27bcc2c
Tx public key: fbae0de81f6d202e50d895b1277a1a6a15902dff7e07b7e511874455a2737df7
Timestamp: 1703130946 Timestamp [UCT]: 2023-12-21 03:55:46 Age [y:d:h:m:s]: 01:348:03:42:46
Block: 917725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507683 RingCT/type: yes/0
Extra: 01fbae0de81f6d202e50d895b1277a1a6a15902dff7e07b7e511874455a2737df70211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7f74a98954fef1fa9eb12f3030dc9675cfae89eeb3e84f6888a0bc5429aa7ec 0.600000000000 1375307 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": 917735, "vin": [ { "gen": { "height": 917725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7f74a98954fef1fa9eb12f3030dc9675cfae89eeb3e84f6888a0bc5429aa7ec" } } ], "extra": [ 1, 251, 174, 13, 232, 31, 109, 32, 46, 80, 216, 149, 177, 39, 122, 26, 106, 21, 144, 45, 255, 126, 7, 183, 229, 17, 135, 68, 85, 162, 115, 125, 247, 2, 17, 0, 0, 0, 6, 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