Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238f9874f98f4fdc0a5ef497df146ed9762496b59f3024cb6d8c03f6edcada0d

Tx prefix hash: f911569ca74c01d37a9dd840d219af6e479c5d96e179316a1735f3efbdb8fa8a
Tx public key: 65c25696e0d9e6c38a308f918b955bafd23a387d1dab294bb9758b7db6381f14
Timestamp: 1723108816 Timestamp [UCT]: 2024-08-08 09:20:16 Age [y:d:h:m:s]: 00:281:21:49:31
Block: 1083332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201397 RingCT/type: yes/0
Extra: 0165c25696e0d9e6c38a308f918b955bafd23a387d1dab294bb9758b7db6381f1402110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166f48d54d48a6082a273be14ef73d5a3c0218c81ec8d1766b3a15c72baabb01 0.600000000000 1557203 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": 1083342, "vin": [ { "gen": { "height": 1083332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166f48d54d48a6082a273be14ef73d5a3c0218c81ec8d1766b3a15c72baabb01" } } ], "extra": [ 1, 101, 194, 86, 150, 224, 217, 230, 195, 138, 48, 143, 145, 139, 149, 91, 175, 210, 58, 56, 125, 29, 171, 41, 75, 185, 117, 139, 125, 182, 56, 31, 20, 2, 17, 0, 0, 0, 12, 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