Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef7d289da97a79c08d266218179af403489465b45e1f49a3403eaac6c81ee157

Tx prefix hash: 78ad99b28abf347a9d11a7cf6c6f0a04af4ecae824ed959f319811397e79b217
Tx public key: fa2927224ae5d3a55de6339d58d6417a37cad2b759b1bee9f5670ba3dc7b9769
Timestamp: 1578816093 Timestamp [UCT]: 2020-01-12 08:01:33 Age [y:d:h:m:s]: 04:320:05:27:43
Block: 43747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118400 RingCT/type: yes/0
Extra: 01fa2927224ae5d3a55de6339d58d6417a37cad2b759b1bee9f5670ba3dc7b976902110000000b8a2ee0d9000000000000000000

1 output(s) for total of 439.591079578000 dcy

stealth address amount amount idx
00: f21537b9f8ab0d6b289c9bb292bf6a668b07cc26d818a7184c1efe3d662e8f52 439.591079578000 79355 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": 43757, "vin": [ { "gen": { "height": 43747 } } ], "vout": [ { "amount": 439591079578, "target": { "key": "f21537b9f8ab0d6b289c9bb292bf6a668b07cc26d818a7184c1efe3d662e8f52" } } ], "extra": [ 1, 250, 41, 39, 34, 74, 229, 211, 165, 93, 230, 51, 157, 88, 214, 65, 122, 55, 202, 210, 183, 89, 177, 190, 233, 245, 103, 11, 163, 220, 123, 151, 105, 2, 17, 0, 0, 0, 11, 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