Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7066c29b4ff10cc85b28a115462cb18bdfaa7b4ad4aafa8ed292e485667bee0b

Tx prefix hash: 8493dfdaa42f5d3a9b33ffc2230fa8dd3164ab1d132d3ca493880af10471e754
Tx public key: 9aacf4652b0cbb67fff2fddb3b9201aa65717aad957b438cf5ba4a5bd89e749f
Timestamp: 1705707522 Timestamp [UCT]: 2024-01-19 23:38:42 Age [y:d:h:m:s]: 01:299:17:07:11
Block: 939030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473039 RingCT/type: yes/0
Extra: 019aacf4652b0cbb67fff2fddb3b9201aa65717aad957b438cf5ba4a5bd89e749f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f16b7fc47c25f22ed67c24e4c89111f0d9b95fc82d96e0eac544220a095a3ef9 0.600000000000 1397114 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": 939040, "vin": [ { "gen": { "height": 939030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f16b7fc47c25f22ed67c24e4c89111f0d9b95fc82d96e0eac544220a095a3ef9" } } ], "extra": [ 1, 154, 172, 244, 101, 43, 12, 187, 103, 255, 242, 253, 219, 59, 146, 1, 170, 101, 113, 122, 173, 149, 123, 67, 140, 245, 186, 74, 91, 216, 158, 116, 159, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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