Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c491e3a133ab3edcb9dcde79e05db753802737a2570c2b42e596e17d1b2f3c3d

Tx prefix hash: b1c2ef12326a6e8c660cb6e75bbe7d64dd0e2441a384bedcba91b4af486b8c47
Tx public key: 3a4cffca6e823ff2a600b7e96eaf30cc5bcc13e8ec0112beda54b1d86bd6a415
Timestamp: 1709942912 Timestamp [UCT]: 2024-03-09 00:08:32 Age [y:d:h:m:s]: 00:347:20:25:07
Block: 974185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248687 RingCT/type: yes/0
Extra: 013a4cffca6e823ff2a600b7e96eaf30cc5bcc13e8ec0112beda54b1d86bd6a4150211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea25be48497cef84292aac01053ed690f4157ac423586b195b8146180ac6b9e9 0.600000000000 1434136 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": 974195, "vin": [ { "gen": { "height": 974185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea25be48497cef84292aac01053ed690f4157ac423586b195b8146180ac6b9e9" } } ], "extra": [ 1, 58, 76, 255, 202, 110, 130, 63, 242, 166, 0, 183, 233, 110, 175, 48, 204, 91, 204, 19, 232, 236, 1, 18, 190, 218, 84, 177, 216, 107, 214, 164, 21, 2, 17, 0, 0, 0, 2, 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