Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac4cc0709fe57888165d7398961c891a49bc8847fc9166d4ee7e50d5ce0fd5f8

Tx prefix hash: 77429025a4d77b529fe5f7c38c07f1d6eb684c3b0d59ece3cb190d2914f9328b
Tx public key: c965b57078731e841b95e0a87f9e61e0353c8196682e5591c1f6dc29aeef8ee2
Timestamp: 1719763250 Timestamp [UCT]: 2024-06-30 16:00:50 Age [y:d:h:m:s]: 00:350:10:56:38
Block: 1055581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250389 RingCT/type: yes/0
Extra: 01c965b57078731e841b95e0a87f9e61e0353c8196682e5591c1f6dc29aeef8ee2021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bf4001db8438b183f9d32bc48accf9a96ac68f6eb77890bd897f22891d618c5 0.600000000000 1525986 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": 1055591, "vin": [ { "gen": { "height": 1055581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bf4001db8438b183f9d32bc48accf9a96ac68f6eb77890bd897f22891d618c5" } } ], "extra": [ 1, 201, 101, 181, 112, 120, 115, 30, 132, 27, 149, 224, 168, 127, 158, 97, 224, 53, 60, 129, 150, 104, 46, 85, 145, 193, 246, 220, 41, 174, 239, 142, 226, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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