Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6d6101faf9c113a4d2167767dbd4f2985e93e669a88f318599fe53c014dcd6

Tx prefix hash: 048ed169e2c685abd7653d6a12a832ac436ff731b34ffc2ed1ecfac0d12c3ea4
Tx public key: f3b20f8fce23a806f0ece1bc5c61472b28160065111cb58455393f3a229e34e0
Timestamp: 1692367734 Timestamp [UCT]: 2023-08-18 14:08:54 Age [y:d:h:m:s]: 01:194:16:00:22
Block: 828646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400250 RingCT/type: yes/0
Extra: 01f3b20f8fce23a806f0ece1bc5c61472b28160065111cb58455393f3a229e34e002110000000375e3f0e9000000000000000000

1 output(s) for total of 1.102432233000 dcy

stealth address amount amount idx
00: fde830f44f43d77078676350813bbc61bacd18b55cbccdab57f7b5e7acd06cd5 1.102432233000 1280978 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": 828656, "vin": [ { "gen": { "height": 828646 } } ], "vout": [ { "amount": 1102432233, "target": { "key": "fde830f44f43d77078676350813bbc61bacd18b55cbccdab57f7b5e7acd06cd5" } } ], "extra": [ 1, 243, 178, 15, 143, 206, 35, 168, 6, 240, 236, 225, 188, 92, 97, 71, 43, 40, 22, 0, 101, 17, 28, 181, 132, 85, 57, 63, 58, 34, 158, 52, 224, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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