Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1124b08e578d8133132b7b093bdcc2c8079a3260f3b9e5bbd498560b4e0a790a

Tx prefix hash: d174acf462c8ecd6fbbfc0a6a2b4b3acaf399d708062f425546290cb8f59ce8a
Tx public key: aa5961e57e89fe5a7647b68792823e9ddd909a0e20875bdb4b3e4f02754c0e6d
Timestamp: 1708320359 Timestamp [UCT]: 2024-02-19 05:25:59 Age [y:d:h:m:s]: 01:100:22:22:48
Block: 960723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333210 RingCT/type: yes/0
Extra: 01aa5961e57e89fe5a7647b68792823e9ddd909a0e20875bdb4b3e4f02754c0e6d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67749bd7d121cf47c2395e0716338852a001e310c4cfa548eb68701d428cd8c0 0.600000000000 1420310 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": 960733, "vin": [ { "gen": { "height": 960723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67749bd7d121cf47c2395e0716338852a001e310c4cfa548eb68701d428cd8c0" } } ], "extra": [ 1, 170, 89, 97, 229, 126, 137, 254, 90, 118, 71, 182, 135, 146, 130, 62, 157, 221, 144, 154, 14, 32, 135, 91, 219, 75, 62, 79, 2, 117, 76, 14, 109, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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