Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c3231b9fa28d48893d45a5c275abbd26b0e070a38851e555bb8970126e45a2

Tx prefix hash: 4ff2685670a2f55424667286a71fc164a84beb4225002bd9de68a97240bfa823
Tx public key: 2fcc428cb590b47e3df984ca3f2a715e65a64c77bc69b880e83d46f3bca6c14f
Timestamp: 1714020270 Timestamp [UCT]: 2024-04-25 04:44:30 Age [y:d:h:m:s]: 00:204:05:53:01
Block: 1007974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146217 RingCT/type: yes/0
Extra: 012fcc428cb590b47e3df984ca3f2a715e65a64c77bc69b880e83d46f3bca6c14f02110000000339e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 519f8e805c7650b5a1c848ae36f9749f003ce376138a9edf77461f8ba2068c07 0.600000000000 1469440 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": 1007984, "vin": [ { "gen": { "height": 1007974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "519f8e805c7650b5a1c848ae36f9749f003ce376138a9edf77461f8ba2068c07" } } ], "extra": [ 1, 47, 204, 66, 140, 181, 144, 180, 126, 61, 249, 132, 202, 63, 42, 113, 94, 101, 166, 76, 119, 188, 105, 184, 128, 232, 61, 70, 243, 188, 166, 193, 79, 2, 17, 0, 0, 0, 3, 57, 225, 213, 211, 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