Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03c3cb67e76d69eab385fad3f533aa629ffda0438000cc823e11195be8c5c958

Tx prefix hash: 78c7b044ef82675dcac1c8edb7eb618e78b1397b7d98dceeb7fd3ff3ed9ca911
Tx public key: 046ef7e34a84a3b0669f559c41ea9c282ab310e8901e78982c27479b256ac957
Timestamp: 1725211951 Timestamp [UCT]: 2024-09-01 17:32:31 Age [y:d:h:m:s]: 00:261:07:28:19
Block: 1100767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186644 RingCT/type: yes/0
Extra: 01046ef7e34a84a3b0669f559c41ea9c282ab310e8901e78982c27479b256ac957021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bde53d1dd4d23d5c7020736dc176ec0fcb8990c03014275ae6e0372d11f4a7ae 0.600000000000 1576748 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": 1100777, "vin": [ { "gen": { "height": 1100767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bde53d1dd4d23d5c7020736dc176ec0fcb8990c03014275ae6e0372d11f4a7ae" } } ], "extra": [ 1, 4, 110, 247, 227, 74, 132, 163, 176, 102, 159, 85, 156, 65, 234, 156, 40, 42, 179, 16, 232, 144, 30, 120, 152, 44, 39, 71, 155, 37, 106, 201, 87, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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