Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3847fb217e13d730da86e07790436562ac7360f0dff49f2954e93fa26978d6ed

Tx prefix hash: 1c9c769f308f1e7cc7c08d4728d7a5870c216448f08ff6b58c0848e41eefdb1c
Tx public key: 8009cf5e1e11172039ccd099c7ac96789f5c30876900724e2dd1364f4edfb3e3
Timestamp: 1582334378 Timestamp [UCT]: 2020-02-22 01:19:38 Age [y:d:h:m:s]: 04:312:01:15:35
Block: 69817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115617 RingCT/type: yes/0
Extra: 018009cf5e1e11172039ccd099c7ac96789f5c30876900724e2dd1364f4edfb3e30211000000084ac5aa02000000000000000000

1 output(s) for total of 360.303184441000 dcy

stealth address amount amount idx
00: 5de0e1fd44b196dad8a371b5bbe0c77e5df75dc6eee4866bf6b40f339e6ad0c3 360.303184441000 128861 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": 69827, "vin": [ { "gen": { "height": 69817 } } ], "vout": [ { "amount": 360303184441, "target": { "key": "5de0e1fd44b196dad8a371b5bbe0c77e5df75dc6eee4866bf6b40f339e6ad0c3" } } ], "extra": [ 1, 128, 9, 207, 94, 30, 17, 23, 32, 57, 204, 208, 153, 199, 172, 150, 120, 159, 92, 48, 135, 105, 0, 114, 78, 45, 209, 54, 79, 78, 223, 179, 227, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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