Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb39e06026a663e483eda4bd7a40778cd55cfbc1291734c1ea88ffdf2e0c437

Tx prefix hash: b79d08e17d7e44b8376ca3f4b8df819c9784ab2446ec06a9dfcf66e8235ce3a2
Tx public key: a5f1d04d3cdeee439d29cd2e2edbc6a0803b3a1674e3c107b1f1540da565b3ae
Timestamp: 1709088597 Timestamp [UCT]: 2024-02-28 02:49:57 Age [y:d:h:m:s]: 01:039:01:52:40
Block: 967102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288922 RingCT/type: yes/0
Extra: 01a5f1d04d3cdeee439d29cd2e2edbc6a0803b3a1674e3c107b1f1540da565b3ae0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163cfbf7e08f47d6c0f95fd045db241b59dcd3dd7b99d65b903e0b710a7607b3 0.600000000000 1426873 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": 967112, "vin": [ { "gen": { "height": 967102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163cfbf7e08f47d6c0f95fd045db241b59dcd3dd7b99d65b903e0b710a7607b3" } } ], "extra": [ 1, 165, 241, 208, 77, 60, 222, 238, 67, 157, 41, 205, 46, 46, 219, 198, 160, 128, 59, 58, 22, 116, 227, 193, 7, 177, 241, 84, 13, 165, 101, 179, 174, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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