Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59729454de7140edad98e999128f4b6c25e891abce4183226bc8f7ed15294562

Tx prefix hash: e9a9e0ad62f92196adce609c98940e2ae5037f055143b26555b598e8c2293a20
Tx public key: 5eb8aef3da3a3b7d0223bd48cf843db0caabb7ead5a72dfe832804826af11d70
Timestamp: 1710618862 Timestamp [UCT]: 2024-03-16 19:54:22 Age [y:d:h:m:s]: 01:008:08:54:18
Block: 979799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266938 RingCT/type: yes/0
Extra: 015eb8aef3da3a3b7d0223bd48cf843db0caabb7ead5a72dfe832804826af11d700211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c13fd2c7a83a2144d556d436f6cd54b9c7dbec3e66fbf20b14e7a8a7fd670b7 0.600000000000 1439854 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": 979809, "vin": [ { "gen": { "height": 979799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c13fd2c7a83a2144d556d436f6cd54b9c7dbec3e66fbf20b14e7a8a7fd670b7" } } ], "extra": [ 1, 94, 184, 174, 243, 218, 58, 59, 125, 2, 35, 189, 72, 207, 132, 61, 176, 202, 171, 183, 234, 213, 167, 45, 254, 131, 40, 4, 130, 106, 241, 29, 112, 2, 17, 0, 0, 0, 5, 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