Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54da5087923ec65a1c0a8d4a80f96714fb95839538f3cbae4c1615ea88238e05

Tx prefix hash: 877d978f9ec2a183d960f6e9c299ddd40f29e604cd49b8e40396d18dca896533
Tx public key: 11438fc85ad8d1e30456e00fdbaa7f4216085854ca6084ff84b919a4af89d0e6
Timestamp: 1703939888 Timestamp [UCT]: 2023-12-30 12:38:08 Age [y:d:h:m:s]: 01:131:05:24:04
Block: 924412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354911 RingCT/type: yes/0
Extra: 0111438fc85ad8d1e30456e00fdbaa7f4216085854ca6084ff84b919a4af89d0e60211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1015ff12a217111b42e6c1321eb1a0264ec58be94532ed4c57a4c3a7b751d26b 0.600000000000 1382160 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": 924422, "vin": [ { "gen": { "height": 924412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1015ff12a217111b42e6c1321eb1a0264ec58be94532ed4c57a4c3a7b751d26b" } } ], "extra": [ 1, 17, 67, 143, 200, 90, 216, 209, 227, 4, 86, 224, 15, 219, 170, 127, 66, 22, 8, 88, 84, 202, 96, 132, 255, 132, 185, 25, 164, 175, 137, 208, 230, 2, 17, 0, 0, 0, 17, 122, 156, 244, 199, 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