Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adaf979dd2114cb03fbb9078123b7ae6635b75f79e037205cc8f01bd70199a4f

Tx prefix hash: f78b9f54c2786093acd49f2dc88a26bf3f960f8fb0c2f305c2a21bfb24965b86
Tx public key: 8c5f432017cc4585f0d356e8fe0ac8f6040e89bdedff967631a3fd4d3cb3c876
Timestamp: 1740321996 Timestamp [UCT]: 2025-02-23 14:46:36 Age [y:d:h:m:s]: 00:226:17:05:11
Block: 1225560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159746 RingCT/type: yes/0
Extra: 018c5f432017cc4585f0d356e8fe0ac8f6040e89bdedff967631a3fd4d3cb3c87602110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a05104a92e83258594eaec035f57acfaeb70cd6900c50b7bb15928992cac373 0.600000000000 1712425 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": 1225570, "vin": [ { "gen": { "height": 1225560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a05104a92e83258594eaec035f57acfaeb70cd6900c50b7bb15928992cac373" } } ], "extra": [ 1, 140, 95, 67, 32, 23, 204, 69, 133, 240, 211, 86, 232, 254, 10, 200, 246, 4, 14, 137, 189, 237, 255, 150, 118, 49, 163, 253, 77, 60, 179, 200, 118, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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