Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39b3407f7d0b248daade43511b6e0f0d9322ad97c563ce7e0180172ffd5d668e

Tx prefix hash: 2639e3a0d0c2b3a01d31f4a8a1269a0f4935707175d51520fccf45e24dcde304
Tx public key: 6060d3b13303ead16fd9305bbf641319fc695ff99fab9a1e83c5a3799d46d535
Timestamp: 1698435698 Timestamp [UCT]: 2023-10-27 19:41:38 Age [y:d:h:m:s]: 01:086:15:05:29
Block: 878989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323094 RingCT/type: yes/0
Extra: 016060d3b13303ead16fd9305bbf641319fc695ff99fab9a1e83c5a3799d46d535021100000016e6d27f9c000000000000000000

1 output(s) for total of 0.750835108000 dcy

stealth address amount amount idx
00: 3f249d4e5bc6a7242043d6950185479da8c8f63782864183e0ab349e43060e63 0.750835108000 1334485 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": 878999, "vin": [ { "gen": { "height": 878989 } } ], "vout": [ { "amount": 750835108, "target": { "key": "3f249d4e5bc6a7242043d6950185479da8c8f63782864183e0ab349e43060e63" } } ], "extra": [ 1, 96, 96, 211, 177, 51, 3, 234, 209, 111, 217, 48, 91, 191, 100, 19, 25, 252, 105, 95, 249, 159, 171, 154, 30, 131, 197, 163, 121, 157, 70, 213, 53, 2, 17, 0, 0, 0, 22, 230, 210, 127, 156, 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