Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18d7af3caeba7d37a82d9f0c5ab9a0322ca4394048fc0fedc7a91730e6ef9964

Tx prefix hash: 0c11458c42c4622004044b6f6d33d96e7d4acf7b339f0d38c75f37166a94fc0c
Tx public key: 71a34a27028ce69124ddda6c43a5f2a4d0e572d24f12cc9649bc577e558d30a3
Timestamp: 1674370764 Timestamp [UCT]: 2023-01-22 06:59:24 Age [y:d:h:m:s]: 02:081:12:37:25
Block: 680139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579918 RingCT/type: yes/0
Extra: 0171a34a27028ce69124ddda6c43a5f2a4d0e572d24f12cc9649bc577e558d30a30211000000045029cbac000000000000000000

1 output(s) for total of 3.423080372000 dcy

stealth address amount amount idx
00: a3e01fd052f46b9c89f0419ece0f1da589eae805ee4108b317d0b58766d0a703 3.423080372000 1122166 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": 680149, "vin": [ { "gen": { "height": 680139 } } ], "vout": [ { "amount": 3423080372, "target": { "key": "a3e01fd052f46b9c89f0419ece0f1da589eae805ee4108b317d0b58766d0a703" } } ], "extra": [ 1, 113, 163, 74, 39, 2, 140, 230, 145, 36, 221, 218, 108, 67, 165, 242, 164, 208, 229, 114, 210, 79, 18, 204, 150, 73, 188, 87, 126, 85, 141, 48, 163, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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