Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ffbb0dd2e5309352262caaa256f40554ae9b787d13466a517a11806252cbee2

Tx prefix hash: e05e14b59c88f2b930444080f40a9d40b7f11b1369002a75d99cd9b5ac71daa2
Tx public key: 1cccf577a0524d0189e780831c95523ccc167c1e82ca6df5744b2b13d9f8aa9e
Timestamp: 1584527636 Timestamp [UCT]: 2020-03-18 10:33:56 Age [y:d:h:m:s]: 04:304:00:14:08
Block: 84925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112900 RingCT/type: yes/0
Extra: 011cccf577a0524d0189e780831c95523ccc167c1e82ca6df5744b2b13d9f8aa9e021100000002e1f32f7d000000000000000000

1 output(s) for total of 321.076857474000 dcy

stealth address amount amount idx
00: 365701111da311215db46eafa800191333a0e44d241971143b2180fa2c3d0ac9 321.076857474000 153713 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": 84935, "vin": [ { "gen": { "height": 84925 } } ], "vout": [ { "amount": 321076857474, "target": { "key": "365701111da311215db46eafa800191333a0e44d241971143b2180fa2c3d0ac9" } } ], "extra": [ 1, 28, 204, 245, 119, 160, 82, 77, 1, 137, 231, 128, 131, 28, 149, 82, 60, 204, 22, 124, 30, 130, 202, 109, 245, 116, 75, 43, 19, 217, 248, 170, 158, 2, 17, 0, 0, 0, 2, 225, 243, 47, 125, 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