Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aee087ef3952a546380f32b3b23e9d5312e88c993513408ce103cb406526f56c

Tx prefix hash: e18c288732bf7d4518585544e648cbe33b8bcb39f50669f0eedd0b7f5ae67bdd
Tx public key: 4c6d80a56101d9091ae6db5d26d5cf70399e50356ba671fbffc6d71670556a12
Timestamp: 1726754680 Timestamp [UCT]: 2024-09-19 14:04:40 Age [y:d:h:m:s]: 00:179:15:20:41
Block: 1113553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128212 RingCT/type: yes/0
Extra: 014c6d80a56101d9091ae6db5d26d5cf70399e50356ba671fbffc6d71670556a12021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 881c3e1d74e14cbd29e684dc7f68207bd062a547b2aa72b5965173ae83a8f2d7 0.600000000000 1593268 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": 1113563, "vin": [ { "gen": { "height": 1113553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "881c3e1d74e14cbd29e684dc7f68207bd062a547b2aa72b5965173ae83a8f2d7" } } ], "extra": [ 1, 76, 109, 128, 165, 97, 1, 217, 9, 26, 230, 219, 93, 38, 213, 207, 112, 57, 158, 80, 53, 107, 166, 113, 251, 255, 198, 215, 22, 112, 85, 106, 18, 2, 17, 0, 0, 0, 3, 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