Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cdb1b098dae1b10bc658c8888a84a7ec2cd7b830447a4ec53bb747fecd6bc27

Tx prefix hash: 1a0f082c28cf1ec3020dd3668ebf47f53e36424210b7f9d10cd6a79d9d809580
Tx public key: 705a7af2238832988336e4c1c942e985507e3378dea5dc744dd975d1c6a5b481
Timestamp: 1706509016 Timestamp [UCT]: 2024-01-29 06:16:56 Age [y:d:h:m:s]: 01:282:07:28:40
Block: 945686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460545 RingCT/type: yes/0
Extra: 01705a7af2238832988336e4c1c942e985507e3378dea5dc744dd975d1c6a5b481021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07ffcecece91dab6d11cf7c75cd09a239eae2e6b70c0d93f0570b4eb03f45cd 0.600000000000 1404002 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": 945696, "vin": [ { "gen": { "height": 945686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07ffcecece91dab6d11cf7c75cd09a239eae2e6b70c0d93f0570b4eb03f45cd" } } ], "extra": [ 1, 112, 90, 122, 242, 35, 136, 50, 152, 131, 54, 228, 193, 201, 66, 233, 133, 80, 126, 51, 120, 222, 165, 220, 116, 77, 217, 117, 209, 198, 165, 180, 129, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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