Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22f457edd8764700b0bcdcee5f1824327563682fb8baede9ba03dc3e29e0e1f8

Tx prefix hash: ed733081441e5700a84872e0f5d7fa0077fe7ee24e2c2a119ea3db7eb4c7bf8a
Tx public key: e1387cbf88d57c121875fa871a6e22c8905edee3832bd44328c299ee1dc3d2e5
Timestamp: 1730018944 Timestamp [UCT]: 2024-10-27 08:49:04 Age [y:d:h:m:s]: 00:027:18:47:45
Block: 1140584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19837 RingCT/type: yes/0
Extra: 01e1387cbf88d57c121875fa871a6e22c8905edee3832bd44328c299ee1dc3d2e5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5334a94a177f54fda54190e822b42d48b13b779e609c7534678f24f5d57ed4c 0.600000000000 1624385 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": 1140594, "vin": [ { "gen": { "height": 1140584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5334a94a177f54fda54190e822b42d48b13b779e609c7534678f24f5d57ed4c" } } ], "extra": [ 1, 225, 56, 124, 191, 136, 213, 124, 18, 24, 117, 250, 135, 26, 110, 34, 200, 144, 94, 222, 227, 131, 43, 212, 67, 40, 194, 153, 238, 29, 195, 210, 229, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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