Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93d83b6da8d3f167f48bf54319935d1d927506ed5a26d2d223c848b720305338

Tx prefix hash: 52c84e959f914d871f644d5db3fa13c1f736972218382d13a3e055320c1714b5
Tx public key: a89e2e205d0d9bb19884b338b2d16d296e5b8f4568017c8e48d2cdcf6ff7f46a
Timestamp: 1717442666 Timestamp [UCT]: 2024-06-03 19:24:26 Age [y:d:h:m:s]: 00:286:07:31:36
Block: 1036363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204611 RingCT/type: yes/0
Extra: 01a89e2e205d0d9bb19884b338b2d16d296e5b8f4568017c8e48d2cdcf6ff7f46a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d03ec297607c947895a7d3e469b93090ab046419856ae371fda5fc4b27d08c9 0.600000000000 1504890 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": 1036373, "vin": [ { "gen": { "height": 1036363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d03ec297607c947895a7d3e469b93090ab046419856ae371fda5fc4b27d08c9" } } ], "extra": [ 1, 168, 158, 46, 32, 93, 13, 155, 177, 152, 132, 179, 56, 178, 209, 109, 41, 110, 91, 143, 69, 104, 1, 124, 142, 72, 210, 205, 207, 111, 247, 244, 106, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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