Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549ed5b48ad7ad2233270e9213bb26b26dd6f76afab0ff77e778833f36811239

Tx prefix hash: 99f37081fb7bf0b37324ce60db8c0b24529773b803c598afb49ec16401e9536f
Tx public key: 6e0cf4bfef3a517bc462664d4f8a7b801cf9f58caaf5c0fbbf058bcf4208b879
Timestamp: 1663452788 Timestamp [UCT]: 2022-09-17 22:13:08 Age [y:d:h:m:s]: 02:186:10:58:25
Block: 590170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654568 RingCT/type: yes/0
Extra: 016e0cf4bfef3a517bc462664d4f8a7b801cf9f58caaf5c0fbbf058bcf4208b879021100000002e6d27f9c000000000000000000

1 output(s) for total of 6.800202929000 dcy

stealth address amount amount idx
00: c8174b0c4038697353541923aa72057eb5d1889a1d62eba7e9e499caa9f46f02 6.800202929000 1024561 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": 590180, "vin": [ { "gen": { "height": 590170 } } ], "vout": [ { "amount": 6800202929, "target": { "key": "c8174b0c4038697353541923aa72057eb5d1889a1d62eba7e9e499caa9f46f02" } } ], "extra": [ 1, 110, 12, 244, 191, 239, 58, 81, 123, 196, 98, 102, 77, 79, 138, 123, 128, 28, 249, 245, 140, 170, 245, 192, 251, 191, 5, 139, 207, 66, 8, 184, 121, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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