Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6029e972a20d227f257679102385340e50adb273a6883d880a014256fdc3d938

Tx prefix hash: e9296be3a6d7e087580c20339b24537b5fe6a4a3355f7cd1aeaf98dd1901a2bb
Tx public key: 54445699dd820a261db416c4698c8187cf33abab3724592e1f72ccea8c97b0d2
Timestamp: 1704951395 Timestamp [UCT]: 2024-01-11 05:36:35 Age [y:d:h:m:s]: 01:303:04:55:07
Block: 932769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475538 RingCT/type: yes/0
Extra: 0154445699dd820a261db416c4698c8187cf33abab3724592e1f72ccea8c97b0d20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66ab4a43aa4302aa4a671c8fb2a5a6bf52de83f8457643caf3eb0db1e1658055 0.600000000000 1390709 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": 932779, "vin": [ { "gen": { "height": 932769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66ab4a43aa4302aa4a671c8fb2a5a6bf52de83f8457643caf3eb0db1e1658055" } } ], "extra": [ 1, 84, 68, 86, 153, 221, 130, 10, 38, 29, 180, 22, 196, 105, 140, 129, 135, 207, 51, 171, 171, 55, 36, 89, 46, 31, 114, 204, 234, 140, 151, 176, 210, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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