Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd560a93de0edb6dbd435f627f3bc68ce9f37d47530782fdb93eed9270d628ef

Tx prefix hash: 4a518aaf4306a56e7dc707a45f0b5ee38aff9511ffef0abb614d7b7e0c5efba2
Tx public key: ca60779b815f3aacd5adcdba43c0cd8a999a01a9325a547b289a2f62d1a35df8
Timestamp: 1707203086 Timestamp [UCT]: 2024-02-06 07:04:46 Age [y:d:h:m:s]: 01:020:22:29:07
Block: 951458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275983 RingCT/type: yes/0
Extra: 01ca60779b815f3aacd5adcdba43c0cd8a999a01a9325a547b289a2f62d1a35df802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab719ccc07de7894d51be36aea6967043b806e71dea8dd6170d4e694423039f5 0.600000000000 1410228 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": 951468, "vin": [ { "gen": { "height": 951458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab719ccc07de7894d51be36aea6967043b806e71dea8dd6170d4e694423039f5" } } ], "extra": [ 1, 202, 96, 119, 155, 129, 95, 58, 172, 213, 173, 205, 186, 67, 192, 205, 138, 153, 154, 1, 169, 50, 90, 84, 123, 40, 154, 47, 98, 209, 163, 93, 248, 2, 17, 0, 0, 0, 3, 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