Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7fb8c668ffd38494142240491e77b7686fdad76c6b4f144c38e69e7753d35b

Tx prefix hash: b7018919a6ed216b937749f8b1a5a03fdeccc335f626e2db74e0e6bf1acd7e5d
Tx public key: 3e440cdac12b9755e90dbb00795cfea5e1ace84e48221913f7f5e9da211ea979
Timestamp: 1574161486 Timestamp [UCT]: 2019-11-19 11:04:46 Age [y:d:h:m:s]: 05:045:08:22:40
Block: 12567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1175509 RingCT/type: yes/0
Extra: 013e440cdac12b9755e90dbb00795cfea5e1ace84e48221913f7f5e9da211ea97902110000000166a80d00000000000000000000

1 output(s) for total of 557.649349474000 dcy

stealth address amount amount idx
00: e55ccc31e0e77a681956ca83c4330b4264033f54273794a86dd92e475a3b936e 557.649349474000 14026 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": 12577, "vin": [ { "gen": { "height": 12567 } } ], "vout": [ { "amount": 557649349474, "target": { "key": "e55ccc31e0e77a681956ca83c4330b4264033f54273794a86dd92e475a3b936e" } } ], "extra": [ 1, 62, 68, 12, 218, 193, 43, 151, 85, 233, 13, 187, 0, 121, 92, 254, 165, 225, 172, 232, 78, 72, 34, 25, 19, 247, 245, 233, 218, 33, 30, 169, 121, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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