Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e7dbfadc5b836e1a1ad665fd44d27e328798bf2b060466f6cc190b8bd1a1d6d

Tx prefix hash: cb7536e860690e4579c913aa397a5cf081e3ddcbb92bdba6c8fa1fc128e60ded
Tx public key: 4220311af57ca42dc94f70900814daabde0fed852e4616b5582bb81737719d9f
Timestamp: 1701205705 Timestamp [UCT]: 2023-11-28 21:08:25 Age [y:d:h:m:s]: 01:154:17:59:42
Block: 901746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371767 RingCT/type: yes/0
Extra: 014220311af57ca42dc94f70900814daabde0fed852e4616b5582bb81737719d9f021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.631162446000 dcy

stealth address amount amount idx
00: 3c35b3874c2ab940c7d8d4c8fbc7edb16ce2905228a617d65f8d404a7abef662 0.631162446000 1358335 of 0

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": 901756, "vin": [ { "gen": { "height": 901746 } } ], "vout": [ { "amount": 631162446, "target": { "key": "3c35b3874c2ab940c7d8d4c8fbc7edb16ce2905228a617d65f8d404a7abef662" } } ], "extra": [ 1, 66, 32, 49, 26, 245, 124, 164, 45, 201, 79, 112, 144, 8, 20, 218, 171, 222, 15, 237, 133, 46, 70, 22, 181, 88, 43, 184, 23, 55, 113, 157, 159, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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