Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9940a297fab66a0db46cb31e83ad885b435e40f4d0ef06c8aaeb589849f8c13

Tx prefix hash: b2fb73aeade278a3cb6e0138f05031dc8df470f5962b1bc86e79d5b907e63de5
Tx public key: 983af774204a29bbedfca7e9da463e480e6a5c97dce5f3e35b7918334072b142
Timestamp: 1733361585 Timestamp [UCT]: 2024-12-05 01:19:45 Age [y:d:h:m:s]: 00:126:00:55:50
Block: 1168235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89873 RingCT/type: yes/0
Extra: 01983af774204a29bbedfca7e9da463e480e6a5c97dce5f3e35b7918334072b14202110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ad48fef05e83bf2e46308f1356803c458662dbe485801e91df7a0c6c1267cc 0.600000000000 1653942 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": 1168245, "vin": [ { "gen": { "height": 1168235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ad48fef05e83bf2e46308f1356803c458662dbe485801e91df7a0c6c1267cc" } } ], "extra": [ 1, 152, 58, 247, 116, 32, 74, 41, 187, 237, 252, 167, 233, 218, 70, 62, 72, 14, 106, 92, 151, 220, 229, 243, 227, 91, 121, 24, 51, 64, 114, 177, 66, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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