Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dac4c20945d6b161685e8be51e8db451f4264e1348ca8aeeda433bea5a62f59

Tx prefix hash: 970e8989fd9eb354cd44275fa67409dbec87a516fcd72d876d895d043e06932f
Tx public key: dc15f0e87241ba05a0cc86c2ee479b6006a755dd3fa11a07fdd26f561d6510ae
Timestamp: 1727941838 Timestamp [UCT]: 2024-10-03 07:50:38 Age [y:d:h:m:s]: 00:211:20:13:40
Block: 1123401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151209 RingCT/type: yes/0
Extra: 01dc15f0e87241ba05a0cc86c2ee479b6006a755dd3fa11a07fdd26f561d6510ae021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1059ea111aad12856518ea25aa8a1c52a90813c06a8129a011e7e8f8122c3511 0.600000000000 1605934 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": 1123411, "vin": [ { "gen": { "height": 1123401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1059ea111aad12856518ea25aa8a1c52a90813c06a8129a011e7e8f8122c3511" } } ], "extra": [ 1, 220, 21, 240, 232, 114, 65, 186, 5, 160, 204, 134, 194, 238, 71, 155, 96, 6, 167, 85, 221, 63, 161, 26, 7, 253, 210, 111, 86, 29, 101, 16, 174, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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