Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d47de5b845c8a6e780ed058e57ae3971a5d6241c77b705cb0bc347ae50e6b07

Tx prefix hash: 8587b0d1a507fea5f91275d8b02181b21ebc1cd9a8cdc63c45dca4af96d499cc
Tx public key: 864764c3788886f472cfe2fb6b1e6c55648b12c32f3ae40a1fa4895ce9eec2b0
Timestamp: 1695775767 Timestamp [UCT]: 2023-09-27 00:49:27 Age [y:d:h:m:s]: 01:117:23:11:46
Block: 856925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345554 RingCT/type: yes/0
Extra: 01864764c3788886f472cfe2fb6b1e6c55648b12c32f3ae40a1fa4895ce9eec2b0021100000002faf35c9c000000000000000000

1 output(s) for total of 0.888488467000 dcy

stealth address amount amount idx
00: e5665e8511fff00975d81251e5c03b82fbe375266f741f0e0a77fc29ad249d06 0.888488467000 1311023 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": 856935, "vin": [ { "gen": { "height": 856925 } } ], "vout": [ { "amount": 888488467, "target": { "key": "e5665e8511fff00975d81251e5c03b82fbe375266f741f0e0a77fc29ad249d06" } } ], "extra": [ 1, 134, 71, 100, 195, 120, 136, 134, 244, 114, 207, 226, 251, 107, 30, 108, 85, 100, 139, 18, 195, 47, 58, 228, 10, 31, 164, 137, 92, 233, 238, 194, 176, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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