Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee34b33c0cb9b96f1b3c5d974b38dc3b3c37e00815cf304d5d916710b7998353

Tx prefix hash: e94ec4388c281435d5b964dd42f3479013e3754f21f320d6dfe85d8bf0d82a5a
Tx public key: 8479dc676e1d1a88a74af0c0a8c40a2420e7a4a19bc3053437322bfe9b057fc8
Timestamp: 1681021511 Timestamp [UCT]: 2023-04-09 06:25:11 Age [y:d:h:m:s]: 01:359:11:36:17
Block: 734680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518177 RingCT/type: yes/0
Extra: 018479dc676e1d1a88a74af0c0a8c40a2420e7a4a19bc3053437322bfe9b057fc80211000000015029cbac000000000000000000

1 output(s) for total of 2.257947654000 dcy

stealth address amount amount idx
00: 50779b8e695517a1fc3f4f68f5cf53c7feee36fb45473533d9f828cbdb7cb41c 2.257947654000 1180921 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": 734690, "vin": [ { "gen": { "height": 734680 } } ], "vout": [ { "amount": 2257947654, "target": { "key": "50779b8e695517a1fc3f4f68f5cf53c7feee36fb45473533d9f828cbdb7cb41c" } } ], "extra": [ 1, 132, 121, 220, 103, 110, 29, 26, 136, 167, 74, 240, 192, 168, 196, 10, 36, 32, 231, 164, 161, 155, 195, 5, 52, 55, 50, 43, 254, 155, 5, 127, 200, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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