Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b7c49b01582970dc9e8e436c09f26f17a747d24c8838fd98cb330bfe11f748

Tx prefix hash: 0ee8dfa731986c05de5c67710e923b03d564e2a4d6b36f5e8836c7aa6d5d0d20
Tx public key: 10c0d85609d39656507a07ef65d46bea28ef7801abd69ddc26eb2f3e801d5c0f
Timestamp: 1713184899 Timestamp [UCT]: 2024-04-15 12:41:39 Age [y:d:h:m:s]: 01:038:01:13:40
Block: 1001050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288175 RingCT/type: yes/0
Extra: 0110c0d85609d39656507a07ef65d46bea28ef7801abd69ddc26eb2f3e801d5c0f02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f07fe5c49ff616eb76ed6609b7e7549272667d474433063e10d00d0084589ce9 0.600000000000 1461552 of 15

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": 1001060, "vin": [ { "gen": { "height": 1001050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f07fe5c49ff616eb76ed6609b7e7549272667d474433063e10d00d0084589ce9" } } ], "extra": [ 1, 16, 192, 216, 86, 9, 211, 150, 86, 80, 122, 7, 239, 101, 212, 107, 234, 40, 239, 120, 1, 171, 214, 157, 220, 38, 235, 47, 62, 128, 29, 92, 15, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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