Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2831f290665dc68dc913fd15d8a7c0fa7219ef6c4a9c1a766f3552cacdb4a9

Tx prefix hash: e114a72b82cf428aaae1fc84675c3b4658d8ac92acf8c4220f53f25bcba8a721
Tx public key: 4735d3f04512b69dff875e2bb6117d238e6c7f2054cfaf018ab7e3ead9919062
Timestamp: 1729254703 Timestamp [UCT]: 2024-10-18 12:31:43 Age [y:d:h:m:s]: 00:020:12:19:50
Block: 1134288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14606 RingCT/type: yes/0
Extra: 014735d3f04512b69dff875e2bb6117d238e6c7f2054cfaf018ab7e3ead99190620211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07b4fb7368e14542c584ebe85fdb3684b8786e9ec4591ae597db713198b2e819 0.600000000000 1617573 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": 1134298, "vin": [ { "gen": { "height": 1134288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07b4fb7368e14542c584ebe85fdb3684b8786e9ec4591ae597db713198b2e819" } } ], "extra": [ 1, 71, 53, 211, 240, 69, 18, 182, 157, 255, 135, 94, 43, 182, 17, 125, 35, 142, 108, 127, 32, 84, 207, 175, 1, 138, 183, 227, 234, 217, 145, 144, 98, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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