Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428e80521d74694ad05c57fb8294471198cf42c1ca72bdff3d2287df1bfd14ac

Tx prefix hash: 070e0931305c3978bcf3b9216caa3ead745636aae7e16414cb952d91e4443e57
Tx public key: f8124bf0868ba71163046d3dcb4924d80c2a0a8bc3f39609755690ec4413261e
Timestamp: 1582643147 Timestamp [UCT]: 2020-02-25 15:05:47 Age [y:d:h:m:s]: 05:253:18:05:52
Block: 72306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1332385 RingCT/type: yes/0
Extra: 01f8124bf0868ba71163046d3dcb4924d80c2a0a8bc3f39609755690ec4413261e0211000000037adf42d3000000000000000000

1 output(s) for total of 353.525712847000 dcy

stealth address amount amount idx
00: 56c03a7ed16a4d255def1e2a2bf8c1fda4a6abd84fc282d34aba041693d12d48 353.525712847000 133500 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": 72316, "vin": [ { "gen": { "height": 72306 } } ], "vout": [ { "amount": 353525712847, "target": { "key": "56c03a7ed16a4d255def1e2a2bf8c1fda4a6abd84fc282d34aba041693d12d48" } } ], "extra": [ 1, 248, 18, 75, 240, 134, 139, 167, 17, 99, 4, 109, 61, 203, 73, 36, 216, 12, 42, 10, 139, 195, 243, 150, 9, 117, 86, 144, 236, 68, 19, 38, 30, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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