Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee993f8cc6ca2659ec2efa7809958e0b57fa57850868fe8fcf5135b1de25799d

Tx prefix hash: 0dabce9b269bf09425dc84c3b7e58482bbb06a43f4e248e9aef0cbd23804cd78
Tx public key: 68617067fabfbb30c073cf0b0cd513cd79e74a5f75ecbd4420270e6b930a957e
Timestamp: 1701375464 Timestamp [UCT]: 2023-11-30 20:17:44 Age [y:d:h:m:s]: 01:185:08:00:04
Block: 903149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393654 RingCT/type: yes/0
Extra: 0168617067fabfbb30c073cf0b0cd513cd79e74a5f75ecbd4420270e6b930a957e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.624442461000 dcy

stealth address amount amount idx
00: 9774fe6929395fe9c19a00bf8b0545e1a4c87b2e6023acecfea573d98efbb8a3 0.624442461000 1359816 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": 903159, "vin": [ { "gen": { "height": 903149 } } ], "vout": [ { "amount": 624442461, "target": { "key": "9774fe6929395fe9c19a00bf8b0545e1a4c87b2e6023acecfea573d98efbb8a3" } } ], "extra": [ 1, 104, 97, 112, 103, 250, 191, 187, 48, 192, 115, 207, 11, 12, 213, 19, 205, 121, 231, 74, 95, 117, 236, 189, 68, 32, 39, 14, 107, 147, 10, 149, 126, 2, 17, 0, 0, 0, 4, 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