Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07dad02dc8786a2bff0be737f13d58401cc5079653353b07a419a730e9aa6ff6

Tx prefix hash: 0b07c38f4558fb9c7a893b7d981b46f237d11415eb2815809e2499250c8b9015
Tx public key: a4385ffcf155f64f04113ed2295796e08f3b3d17643ff212b32d5966c6b638b5
Timestamp: 1579197419 Timestamp [UCT]: 2020-01-16 17:56:59 Age [y:d:h:m:s]: 05:293:07:24:27
Block: 46984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357471 RingCT/type: yes/0
Extra: 01a4385ffcf155f64f04113ed2295796e08f3b3d17643ff212b32d5966c6b638b50211000000012264afe6000000000000000000

1 output(s) for total of 428.867702627000 dcy

stealth address amount amount idx
00: a81b50cb2bdd2a46b904aa57b692d8d6150697896d275f1718978d126f8bc5c4 428.867702627000 86714 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": 46994, "vin": [ { "gen": { "height": 46984 } } ], "vout": [ { "amount": 428867702627, "target": { "key": "a81b50cb2bdd2a46b904aa57b692d8d6150697896d275f1718978d126f8bc5c4" } } ], "extra": [ 1, 164, 56, 95, 252, 241, 85, 246, 79, 4, 17, 62, 210, 41, 87, 150, 224, 143, 59, 61, 23, 100, 63, 242, 18, 179, 45, 89, 102, 198, 182, 56, 181, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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