Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6acc4cccd14fceb19227d6fd346525a4ad85b2f52d6f96fe69f18c4b5a84935e

Tx prefix hash: 46f25de6ea4f1d61efcd04145b0c2b21dfd3babace9763128a56dac3c29c7529
Tx public key: f2e59f654707b5e06374eed5e68f1dbbbf052645d5fbfaeadca2505c6ebfdf5d
Timestamp: 1725129434 Timestamp [UCT]: 2024-08-31 18:37:14 Age [y:d:h:m:s]: 00:238:19:32:13
Block: 1100075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170558 RingCT/type: yes/0
Extra: 01f2e59f654707b5e06374eed5e68f1dbbbf052645d5fbfaeadca2505c6ebfdf5d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6d352e1cecefd98e0974e5af0fef5d5dfa74f8c873fc9b5e88f7e7d169b1058 0.600000000000 1576048 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": 1100085, "vin": [ { "gen": { "height": 1100075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6d352e1cecefd98e0974e5af0fef5d5dfa74f8c873fc9b5e88f7e7d169b1058" } } ], "extra": [ 1, 242, 229, 159, 101, 71, 7, 181, 224, 99, 116, 238, 213, 230, 143, 29, 187, 191, 5, 38, 69, 213, 251, 250, 234, 220, 162, 80, 92, 110, 191, 223, 93, 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