Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe85c5c627e2068ff7830b2d55046efd2f7a1f2b3dccdc4678f55cd65f89d44

Tx prefix hash: c24a46e6865d7ba2248c9fe66481de11c793bb916d0c8a316414dc50d1f290a7
Tx public key: e5df94ab41ca8e45d57cd566a7bd01849d2f356045518ebe31beddc54b99dda1
Timestamp: 1721132036 Timestamp [UCT]: 2024-07-16 12:13:56 Age [y:d:h:m:s]: 00:131:06:10:35
Block: 1066962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93898 RingCT/type: yes/0
Extra: 01e5df94ab41ca8e45d57cd566a7bd01849d2f356045518ebe31beddc54b99dda102110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1a8c2aea78e3d95fbc26cb3bd59d2705b2815edcdad1da0c626e2afab53072e 0.600000000000 1537645 of 15

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": 1066972, "vin": [ { "gen": { "height": 1066962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1a8c2aea78e3d95fbc26cb3bd59d2705b2815edcdad1da0c626e2afab53072e" } } ], "extra": [ 1, 229, 223, 148, 171, 65, 202, 142, 69, 213, 124, 213, 102, 167, 189, 1, 132, 157, 47, 53, 96, 69, 81, 142, 190, 49, 190, 221, 197, 75, 153, 221, 161, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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