Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24027c6ec513eb4b734821427e258e20d2f3e88acaf511976bded0c8d38d09e

Tx prefix hash: d5399ce9e879fd7dcfc1861406a275cc2e012310314f159e5503e633005132fb
Tx public key: 0c1c7e68449dd1cd65df394744a27c884fd301b01016f73c8bc1ea5a6dac9b93
Timestamp: 1735731922 Timestamp [UCT]: 2025-01-01 11:45:22 Age [y:d:h:m:s]: 00:320:17:17:06
Block: 1187845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226743 RingCT/type: yes/0
Extra: 010c1c7e68449dd1cd65df394744a27c884fd301b01016f73c8bc1ea5a6dac9b930211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caeadd4da41ffcd0dfe9c4cf3d914823dd06dd2df5affee86fb5cfb7f32e93c8 0.600000000000 1674342 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": 1187855, "vin": [ { "gen": { "height": 1187845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caeadd4da41ffcd0dfe9c4cf3d914823dd06dd2df5affee86fb5cfb7f32e93c8" } } ], "extra": [ 1, 12, 28, 126, 104, 68, 157, 209, 205, 101, 223, 57, 71, 68, 162, 124, 136, 79, 211, 1, 176, 16, 22, 247, 60, 139, 193, 234, 90, 109, 172, 155, 147, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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