Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94020c0de84201070dae7071de37904b63bbdce34a33a48c2d83d9c78039cd91

Tx prefix hash: 9ee81e4bd73364a5264cb2a9e40b4e3cab014bd88b434c99131d3ed55fe0be68
Tx public key: 6001e99158398f449ae6bee8daf1bc55e421786bbfe007f6b9a9daa48a1ac833
Timestamp: 1694778175 Timestamp [UCT]: 2023-09-15 11:42:55 Age [y:d:h:m:s]: 02:082:00:10:06
Block: 848635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 578336 RingCT/type: yes/0
Extra: 016001e99158398f449ae6bee8daf1bc55e421786bbfe007f6b9a9daa48a1ac83302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.946498693000 dcy

stealth address amount amount idx
00: 102e82b974e9cc424309091a4b6c230fd1e4b6f300210ec02d6e18417935d9ab 0.946498693000 1302251 of 0

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": 848645, "vin": [ { "gen": { "height": 848635 } } ], "vout": [ { "amount": 946498693, "target": { "key": "102e82b974e9cc424309091a4b6c230fd1e4b6f300210ec02d6e18417935d9ab" } } ], "extra": [ 1, 96, 1, 233, 145, 88, 57, 143, 68, 154, 230, 190, 232, 218, 241, 188, 85, 228, 33, 120, 107, 191, 224, 7, 246, 185, 169, 218, 164, 138, 26, 200, 51, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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