Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a19832509655f2b3f3f309e6acfd8ec8266da976f8d9366bd5c435d087f325

Tx prefix hash: f43542e989154731489792a02319b4f9ed0b1b09a91ec51529ad0d4544dc22f6
Tx public key: ce1d09f850acae098ae66398d7b8e6dd4c6809fa0c76e80c49ed57753d2f18f8
Timestamp: 1704821045 Timestamp [UCT]: 2024-01-09 17:24:05 Age [y:d:h:m:s]: 01:110:16:23:23
Block: 931699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340242 RingCT/type: yes/0
Extra: 01ce1d09f850acae098ae66398d7b8e6dd4c6809fa0c76e80c49ed57753d2f18f80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6fd69558c16c290895901ed5189746fb4451c5372b042b0653fe302ab0d2f3e 0.600000000000 1389603 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": 931709, "vin": [ { "gen": { "height": 931699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6fd69558c16c290895901ed5189746fb4451c5372b042b0653fe302ab0d2f3e" } } ], "extra": [ 1, 206, 29, 9, 248, 80, 172, 174, 9, 138, 230, 99, 152, 215, 184, 230, 221, 76, 104, 9, 250, 12, 118, 232, 12, 73, 237, 87, 117, 61, 47, 24, 248, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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