Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c6f7dd5ba42354b6d9a87136886cd1b1fe908f4652df234f56b573358b84a29

Tx prefix hash: 06a78e82892325ac98aeb03c1d57b281ca62ef6d79c8b1efe106ce19ad101c94
Tx public key: e33e807f88a3aa151d86073cd699ccbffe7d52b2311db3b840728343dbb1e4a3
Timestamp: 1707646611 Timestamp [UCT]: 2024-02-11 10:16:51 Age [y:d:h:m:s]: 01:049:14:41:24
Block: 955128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296503 RingCT/type: yes/0
Extra: 01e33e807f88a3aa151d86073cd699ccbffe7d52b2311db3b840728343dbb1e4a302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98d13ddf6145f2ca29e21528eea262cad86851153f881fcb948e82159aa2c5f 0.600000000000 1414414 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": 955138, "vin": [ { "gen": { "height": 955128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98d13ddf6145f2ca29e21528eea262cad86851153f881fcb948e82159aa2c5f" } } ], "extra": [ 1, 227, 62, 128, 127, 136, 163, 170, 21, 29, 134, 7, 60, 214, 153, 204, 191, 254, 125, 82, 178, 49, 29, 179, 184, 64, 114, 131, 67, 219, 177, 228, 163, 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