Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05bc6abf40e1c84f0ec35174c7921330ffae906f6e383df37707d0b0ce4a29f9

Tx prefix hash: 2c4057e896cb165ae37128726581365ed3d8f7e5f363d900575de78f9ae65217
Tx public key: 47ed165297231c4361fdcbe30395b1e11f38e522f700f09c13b4b582bc3ea972
Timestamp: 1723536678 Timestamp [UCT]: 2024-08-13 08:11:18 Age [y:d:h:m:s]: 01:092:03:23:35
Block: 1086880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324326 RingCT/type: yes/0
Extra: 0147ed165297231c4361fdcbe30395b1e11f38e522f700f09c13b4b582bc3ea972021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 153210acd26b5eae33ca1d22eb1eeb58cc331ba5296cc2d68e2d307d966f5e09 0.600000000000 1561479 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": 1086890, "vin": [ { "gen": { "height": 1086880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "153210acd26b5eae33ca1d22eb1eeb58cc331ba5296cc2d68e2d307d966f5e09" } } ], "extra": [ 1, 71, 237, 22, 82, 151, 35, 28, 67, 97, 253, 203, 227, 3, 149, 177, 225, 31, 56, 229, 34, 247, 0, 240, 156, 19, 180, 181, 130, 188, 62, 169, 114, 2, 17, 0, 0, 0, 5, 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