Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbf987a8fc77f434fb5aa89466426f22f3d4b3995c20fcfad6b8c70d9615084

Tx prefix hash: 62f1a04f8187b15bd669c001e91a69df6ce116d0560aff11bcd3a333eed757e5
Tx public key: 59da7ee8d077ffcddaf98f4d4955184f350c43f3e7b479b1c276d5c6b4fbcf1e
Timestamp: 1735142919 Timestamp [UCT]: 2024-12-25 16:08:39 Age [y:d:h:m:s]: 00:095:22:17:26
Block: 1182982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68333 RingCT/type: yes/0
Extra: 0159da7ee8d077ffcddaf98f4d4955184f350c43f3e7b479b1c276d5c6b4fbcf1e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c73870a83cc008d11fe6ef0addc61a46ac3479266450238a3aca96c769d676d6 0.600000000000 1669421 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": 1182992, "vin": [ { "gen": { "height": 1182982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c73870a83cc008d11fe6ef0addc61a46ac3479266450238a3aca96c769d676d6" } } ], "extra": [ 1, 89, 218, 126, 232, 208, 119, 255, 205, 218, 249, 143, 77, 73, 85, 24, 79, 53, 12, 67, 243, 231, 180, 121, 177, 194, 118, 213, 198, 180, 251, 207, 30, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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