Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 889b5a0a975f95fd4a717dd5b0e2fd9eccaafa8df05f2918a3eb73358b3a9d5e

Tx prefix hash: 400c688f405d4c2b4154e57d77c27faae1dc9fdd3a82e7325cf911698dccc904
Tx public key: f2dcc3c4dbcbb63056814f711d869b905b4a313f868bd3aaadd13029b4cd0c59
Timestamp: 1682286373 Timestamp [UCT]: 2023-04-23 21:46:13 Age [y:d:h:m:s]: 01:356:00:46:54
Block: 745141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515736 RingCT/type: yes/0
Extra: 01f2dcc3c4dbcbb63056814f711d869b905b4a313f868bd3aaadd13029b4cd0c59021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.084676902000 dcy

stealth address amount amount idx
00: 3884588b99b61a40f201d6b334632d84cb6d050dbae81023f0fe5e8c5913d5e9 2.084676902000 1192562 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": 745151, "vin": [ { "gen": { "height": 745141 } } ], "vout": [ { "amount": 2084676902, "target": { "key": "3884588b99b61a40f201d6b334632d84cb6d050dbae81023f0fe5e8c5913d5e9" } } ], "extra": [ 1, 242, 220, 195, 196, 219, 203, 182, 48, 86, 129, 79, 113, 29, 134, 155, 144, 91, 74, 49, 63, 134, 139, 211, 170, 173, 209, 48, 41, 180, 205, 12, 89, 2, 17, 0, 0, 0, 1, 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