Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44433d9d0d2b91a30a9fe8ceb28d28e5f50ad00b0a96864bf27711bc38cb89d4

Tx prefix hash: e61cfe043267e7787c95000c430e8fb402184c8f16defa03c990f5a3493057fb
Tx public key: 97ff2dea6442e25fe1f58c0922191e78e4542dcde571bc838eb61718fd358321
Timestamp: 1708305027 Timestamp [UCT]: 2024-02-19 01:10:27 Age [y:d:h:m:s]: 01:066:07:49:52
Block: 960595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308449 RingCT/type: yes/0
Extra: 0197ff2dea6442e25fe1f58c0922191e78e4542dcde571bc838eb61718fd35832102110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d279493f71e2ccba0e17c5e83b2478d379a7a2082bef3afc9c7be129f8950b8 0.600000000000 1420180 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": 960605, "vin": [ { "gen": { "height": 960595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d279493f71e2ccba0e17c5e83b2478d379a7a2082bef3afc9c7be129f8950b8" } } ], "extra": [ 1, 151, 255, 45, 234, 100, 66, 226, 95, 225, 245, 140, 9, 34, 25, 30, 120, 228, 84, 45, 205, 229, 113, 188, 131, 142, 182, 23, 24, 253, 53, 131, 33, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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