Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c6426da5fcc13a4a4029d99bcb87b786cfa451abc57af503335d4b940bf5af

Tx prefix hash: f7a694a9d8ca7e67d1fd3d861d63080fb13068372659f3c7cf56a6e82b403271
Tx public key: 885d36efb52d58c6d7fe540567558dd16e9a39aca0027d85d7944a7d6ca5d0b9
Timestamp: 1669785005 Timestamp [UCT]: 2022-11-30 05:10:05 Age [y:d:h:m:s]: 02:139:11:18:24
Block: 642168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621368 RingCT/type: yes/0
Extra: 01885d36efb52d58c6d7fe540567558dd16e9a39aca0027d85d7944a7d6ca5d0b9021100000009e6d27f9c000000000000000000

1 output(s) for total of 4.573312070000 dcy

stealth address amount amount idx
00: 44e0d5cbc67871328d5c82cf3d23ce7e6fbaa36f979eb4ce02f149f5838ec6b8 4.573312070000 1082035 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": 642178, "vin": [ { "gen": { "height": 642168 } } ], "vout": [ { "amount": 4573312070, "target": { "key": "44e0d5cbc67871328d5c82cf3d23ce7e6fbaa36f979eb4ce02f149f5838ec6b8" } } ], "extra": [ 1, 136, 93, 54, 239, 181, 45, 88, 198, 215, 254, 84, 5, 103, 85, 141, 209, 110, 154, 57, 172, 160, 2, 125, 133, 215, 148, 74, 125, 108, 165, 208, 185, 2, 17, 0, 0, 0, 9, 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