Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ef213dfd65cd3a8e8e77cc17cfaa8481c2d664a0d18de1b8daf473f5ec5e171

Tx prefix hash: fb2b1436e014b3d2347a1594b6660527b193f506c7af2332d79c1ea2876399cf
Tx public key: fb1b1d2061c262d1e5567c76416c79a0f96d43de5abda24db2962ada561051fe
Timestamp: 1738682014 Timestamp [UCT]: 2025-02-04 15:13:34 Age [y:d:h:m:s]: 00:037:02:41:06
Block: 1211999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26568 RingCT/type: yes/0
Extra: 01fb1b1d2061c262d1e5567c76416c79a0f96d43de5abda24db2962ada561051fe0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 139143cf101b294dfb1b8782847d94e5d53e5fd423f367cafdcec7d64c3a6eb6 0.600000000000 1698766 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": 1212009, "vin": [ { "gen": { "height": 1211999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "139143cf101b294dfb1b8782847d94e5d53e5fd423f367cafdcec7d64c3a6eb6" } } ], "extra": [ 1, 251, 27, 29, 32, 97, 194, 98, 209, 229, 86, 124, 118, 65, 108, 121, 160, 249, 109, 67, 222, 90, 189, 162, 77, 178, 150, 42, 218, 86, 16, 81, 254, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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