Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9848e673130923dee6187284148e6b76ee3af5ff928016f73e2a2214c969af03

Tx prefix hash: 10805b7355ed801333cdf0de0f87e8982364082ca3b2bf513c0d68d1e35e4b88
Tx public key: c82d167d8ce22139d71bbb13ea3f072afc7ff300cb9b4bc93d7c7fc335506f58
Timestamp: 1714415977 Timestamp [UCT]: 2024-04-29 18:39:37 Age [y:d:h:m:s]: 01:206:22:25:07
Block: 1011255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406544 RingCT/type: yes/0
Extra: 01c82d167d8ce22139d71bbb13ea3f072afc7ff300cb9b4bc93d7c7fc335506f580211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcd696a025319a5cb3f8f4f293642d436973153392d2c0a57350cb525f4e5f98 0.600000000000 1473437 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": 1011265, "vin": [ { "gen": { "height": 1011255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcd696a025319a5cb3f8f4f293642d436973153392d2c0a57350cb525f4e5f98" } } ], "extra": [ 1, 200, 45, 22, 125, 140, 226, 33, 57, 215, 27, 187, 19, 234, 63, 7, 42, 252, 127, 243, 0, 203, 155, 75, 201, 61, 124, 127, 195, 53, 80, 111, 88, 2, 17, 0, 0, 0, 1, 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