Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e269eea9e770f2662b7765626444fe572095cc08f88c27b963db109fd04fb818

Tx prefix hash: c68ab81bb12f3ea079a7abbdcf2e655784cf50995b2c934a0a8fa6148939bf16
Tx public key: 6e09541e8584dae0476f8b49f98c9c1a898c2b0474ddb76daedce46a572fc1a1
Timestamp: 1720543279 Timestamp [UCT]: 2024-07-09 16:41:19 Age [y:d:h:m:s]: 00:328:22:26:04
Block: 1062067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235067 RingCT/type: yes/0
Extra: 016e09541e8584dae0476f8b49f98c9c1a898c2b0474ddb76daedce46a572fc1a1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80dc2b3210a9e9f4a80702e9d927dac818014088d9901022229c18b25f082ac1 0.600000000000 1532568 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": 1062077, "vin": [ { "gen": { "height": 1062067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80dc2b3210a9e9f4a80702e9d927dac818014088d9901022229c18b25f082ac1" } } ], "extra": [ 1, 110, 9, 84, 30, 133, 132, 218, 224, 71, 111, 139, 73, 249, 140, 156, 26, 137, 140, 43, 4, 116, 221, 183, 109, 174, 220, 228, 106, 87, 47, 193, 161, 2, 17, 0, 0, 0, 1, 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