Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 259d96f6cad7dd07bbb487684b36f56fecb5f3316a6c75898961dff9f96eb939

Tx prefix hash: 808b0b311ac534442dc4cac54e0efd8761deb4d6f2d05b321a18630f3d8705d2
Tx public key: e8438d9385ca80a942b089429a5eec76fe987de351a4c1ab69571491679bc7b3
Timestamp: 1711603883 Timestamp [UCT]: 2024-03-28 05:31:23 Age [y:d:h:m:s]: 01:223:04:43:53
Block: 987968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418161 RingCT/type: yes/0
Extra: 01e8438d9385ca80a942b089429a5eec76fe987de351a4c1ab69571491679bc7b302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5b43eac38150a4d64a8c1529f8ff5ac0d2bf5b4b033ad19c6297e78a8accdf6 0.600000000000 1448229 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": 987978, "vin": [ { "gen": { "height": 987968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5b43eac38150a4d64a8c1529f8ff5ac0d2bf5b4b033ad19c6297e78a8accdf6" } } ], "extra": [ 1, 232, 67, 141, 147, 133, 202, 128, 169, 66, 176, 137, 66, 154, 94, 236, 118, 254, 152, 125, 227, 81, 164, 193, 171, 105, 87, 20, 145, 103, 155, 199, 179, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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