Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 221a91487f1a21bfb4f354ef8279922132e811d107b154312bca1b92fc9bb5fc

Tx prefix hash: c7e8b1fa9bea7244d00bab44d78b749ffa27dda17fa2f744c2a9e37f9377baf6
Tx public key: 0dfd51364283a91ee0672207c603c604fe62e7dc1629449399e26caa93be1e9a
Timestamp: 1677046142 Timestamp [UCT]: 2023-02-22 06:09:02 Age [y:d:h:m:s]: 02:258:18:35:49
Block: 702334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704241 RingCT/type: yes/0
Extra: 010dfd51364283a91ee0672207c603c604fe62e7dc1629449399e26caa93be1e9a02110000000233af99f4000000000000000000

1 output(s) for total of 2.889853422000 dcy

stealth address amount amount idx
00: 64d9e9fc2b66f65e715d9c8bf377b9f69e787a2f8423302ef10f142d292d5d2b 2.889853422000 1145833 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": 702344, "vin": [ { "gen": { "height": 702334 } } ], "vout": [ { "amount": 2889853422, "target": { "key": "64d9e9fc2b66f65e715d9c8bf377b9f69e787a2f8423302ef10f142d292d5d2b" } } ], "extra": [ 1, 13, 253, 81, 54, 66, 131, 169, 30, 224, 103, 34, 7, 198, 3, 198, 4, 254, 98, 231, 220, 22, 41, 68, 147, 153, 226, 108, 170, 147, 190, 30, 154, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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