Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd015394cef75e81ae1a145a4953cf49313294ccab18e334ef7378191a2050df

Tx prefix hash: 06979bf8f7e1960330ecfe633b5db5c5a721d488364f0a8e70f38c396dd914e6
Tx public key: f6b859ec2acee0e746d0a5f7faf7183ddf112581221598a36fe53b7f57e7c978
Timestamp: 1577709797 Timestamp [UCT]: 2019-12-30 12:43:17 Age [y:d:h:m:s]: 05:004:06:05:44
Block: 35026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153030 RingCT/type: yes/0
Extra: 01f6b859ec2acee0e746d0a5f7faf7183ddf112581221598a36fe53b7f57e7c9780211000000028a2ee0d9000000000000000000

1 output(s) for total of 469.834795375000 dcy

stealth address amount amount idx
00: 043196f83501e49ddce43deecb6cf4a549314a35ed64aa04d2d4cfbce5d9690c 469.834795375000 59011 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": 35036, "vin": [ { "gen": { "height": 35026 } } ], "vout": [ { "amount": 469834795375, "target": { "key": "043196f83501e49ddce43deecb6cf4a549314a35ed64aa04d2d4cfbce5d9690c" } } ], "extra": [ 1, 246, 184, 89, 236, 42, 206, 224, 231, 70, 208, 165, 247, 250, 247, 24, 61, 223, 17, 37, 129, 34, 21, 152, 163, 111, 229, 59, 127, 87, 231, 201, 120, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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