Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a979ddee5871c099da5db7210c5d2169def5ce473e7b34d46682ec2fb849193

Tx prefix hash: 1c26c63f93d10c0551a55a89f828079e15fca738dc8eee4d9d1f6a33d6937c00
Tx public key: a376d09dc260e12fc83a49ffc62c8f6c074b6555bd97372b7faf18e80e0c7f16
Timestamp: 1697277421 Timestamp [UCT]: 2023-10-14 09:57:01 Age [y:d:h:m:s]: 01:141:22:08:40
Block: 869380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362443 RingCT/type: yes/0
Extra: 01a376d09dc260e12fc83a49ffc62c8f6c074b6555bd97372b7faf18e80e0c7f1602110000000133af99f4000000000000000000

1 output(s) for total of 0.807947593000 dcy

stealth address amount amount idx
00: afb8f8d4983db0cbdcfdb1267d2ebc8ee92ac6817fd064701eaccab14e82f188 0.807947593000 1324225 of 0

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": 869390, "vin": [ { "gen": { "height": 869380 } } ], "vout": [ { "amount": 807947593, "target": { "key": "afb8f8d4983db0cbdcfdb1267d2ebc8ee92ac6817fd064701eaccab14e82f188" } } ], "extra": [ 1, 163, 118, 208, 157, 194, 96, 225, 47, 200, 58, 73, 255, 198, 44, 143, 108, 7, 75, 101, 85, 189, 151, 55, 43, 127, 175, 24, 232, 14, 12, 127, 22, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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